Pushed up some changes to prevent "bitrot" with hardcoded references to ever-changing models and collections.

But... blocking this pending further discussion, because:

I am unsure about all the client library usage.. there's a lot of usage in this PR that won't work with the new Stainless SDKs, and advertising these features in a skill would just create more debt for us later if we plan to ship those.

We don't really have a plan around what we're doing with our old and new Replicate client libraries in this new Cloudflare world.. my inclination is to let the alpha and beta Stainless SDKs die on the vine, because it won't be worth the disruption to users, especially if they're gonna have to migrate from Replicate API to Cloudflare API at some point anyway...

My inclination would be to keep the SDKs out of these skills entirely. Let the agents write code directly against the HTTP API. They won't get much benefit from the SDKs, and the API is way more stable and easy to reason about.

@andreasjansson as you mentioned in chat:

we can just update the skill and people’s agents will keep working (as opposed to the fixed-in-time knowledge the agent is pretrained with)

With that in mind, I'm okay with shipping this, but the changes as they are seem heavy-handed. I'd love to keep the skills lean so agents know everything they need to know to "self serve", instead of us feeding them a large and potentially overly prescriptive pile of docs full of subtleties that can lead them astray, like code snippets implicitly recommending models that will soon be outmoded.